chore(deps): bump actions/cache/save from 5.0.5 to 6.1.0 by dependabot[bot] · Pull Request #320 · pleaseai/soop

dependabot · 2026-07-01T16:58:08Z

Bumps actions/cache/save from 5.0.5 to 6.1.0.

Release notes

Sourced from actions/cache/save's releases.

v6.1.0

What's Changed

Bump @actions/cache to v6.1.0 - handle read-only cache access by @jasongin in actions/cache#1768

Full Changelog: actions/cache@v6...v6.1.0

v6.0.0

What's Changed

Update packages, migrate to ESM by @Samirat in actions/cache#1760

Full Changelog: actions/cache@v5...v6.0.0

v5.1.0

What's Changed

Bump @actions/cache to v5.1.0 - handle read-only cache access by @jasongin in actions/cache#1775

Full Changelog: actions/cache@v5...v5.1.0

Changelog

Sourced from actions/cache/save's changelog.

Releases

How to prepare a release

[!NOTE] Relevant for maintainers with write access only.

Switch to a new branch from main.

Run npm test to ensure all tests are passing.

Update the version in https://github.com/actions/cache/blob/main/package.json.

Run npm run build to update the compiled files.

Update this https://github.com/actions/cache/blob/main/RELEASES.md with the new version and changes in the ## Changelog section.

Run licensed cache to update the license report.

Run licensed status and resolve any warnings by updating the https://github.com/actions/cache/blob/main/.licensed.yml file with the exceptions.

Commit your changes and push your branch upstream.

Open a pull request against main and get it reviewed and merged.

Draft a new release https://github.com/actions/cache/releases use the same version number used in package.json

Create a new tag with the version number.

Auto generate release notes and update them to match the changes you made in RELEASES.md.

Toggle the set as the latest release option.

Publish the release.

Navigate to https://github.com/actions/cache/actions/workflows/release-new-action-version.yml

There should be a workflow run queued with the same version number.

Approve the run to publish the new version and update the major tags for this action.

Changelog

6.1.0

Bump @actions/cache to v6.1.0 to pick up actions/toolkit#2435 Handle cache write error due to read-only token

Switch redundant "Cache save failed" warning to debug log in save-only

6.0.0

Updated @actions/cache to ^6.0.1, @actions/core to ^3.0.1, @actions/exec to ^3.0.0, @actions/io to ^3.0.2

Migrated to ESM module system

Upgraded Jest to v30 and test infrastructure to be ESM compatible

5.0.4

Bump minimatch to v3.1.5 (fixes ReDoS via globstar patterns)

Bump undici to v6.24.1 (WebSocket decompression bomb protection, header validation fixes)

Bump fast-xml-parser to v5.5.6

5.0.3

Bump @actions/cache to v5.0.5 (Resolves: https://github.com/actions/cache/security/dependabot/33)

Bump @actions/core to v2.0.3

5.0.2

... (truncated)

Commits

55cc834 Merge pull request #1768 from jasongin/readonly-cache
d8cd72f Bump @actions/cache to v6.1.0 - handle cache write error due to RO token
2c8a9bd Merge pull request #1760 from actions/samirat/esm_migration_and_package_update
e9b91fd Prettier fixes
e4884b8 Rebuild dist
10baf01 Fixed licenses
e39b386 Fix test mock return order
b692820 PR feedback
6074912 Rebuild dist bundles as ESM to match type:module
5a912e8 Fix lint and jest issues
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by cubic

Upgrade actions/cache/save to 6.1.0 in the soop-encode workflow to improve cache save reliability (handles read‑only tokens) and reduce noisy warnings.

Dependencies
- Updated .github/workflows/soop-encode.yml: actions/cache/save 5.0.5 → 6.1.0

^{Written for commit f7937e4. Summary will update on new commits.}

Bumps [actions/cache/save](https://github.com/actions/cache) from 5.0.5 to 6.1.0. - [Release notes](https://github.com/actions/cache/releases) - [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md) - [Commits](actions/cache@27d5ce7...55cc834) --- updated-dependencies: - dependency-name: actions/cache/save dependency-version: 6.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

greptile-apps · 2026-07-01T16:59:48Z

Greptile Summary

This PR bumps actions/cache/save from v5.0.5 to v6.1.0 in the soop-encode workflow. The v6.1.0 release adds graceful handling of cache-write errors when the token is read-only and migrated to ESM in v6.0.0.

Confidence Score: 4/5

Safe to merge — the v6.1.0 save action is a backward-compatible improvement that gracefully handles read-only token errors, and the workflow's cache restore path is unaffected.

The only changed lines are two pinned hashes for the cache save steps. The inline version comments still say # v5 despite the bump to v6.1.0, and the corresponding restore steps were not bumped to match, leaving the workflow with mixed major versions across restore and save. Neither issue affects runtime correctness, but they add friction for future audits.

.github/workflows/soop-encode.yml — the restore steps at lines 59 and 69 should ideally be bumped alongside the save steps, and the # v5 comments on lines 105 and 112 need updating.

Important Files Changed

Filename	Overview
.github/workflows/soop-encode.yml	Bumps `actions/cache/save` commit pin from v5.0.5 to v6.1.0 in both save steps; restore steps remain on the old v5 hash and the inline `# v5` comments were not updated to reflect the new major version.

Comments Outside Diff (1)

.github/workflows/soop-encode.yml, line 59-73 (link)

restore steps still pinned to v5 while save steps are now v6

The two actions/cache/restore steps still use the old hash (27d5ce7f / v5), while the corresponding save steps were bumped to v6.1.0. Although restore and save are independent actions and backward-compatible in practice, having them at different major versions is inconsistent and makes auditing the dependency harder. Consider bumping the restore steps to the same major version.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/soop-encode.yml
Line: 59-73

Comment:
**`restore` steps still pinned to v5 while `save` steps are now v6**

The two `actions/cache/restore` steps still use the old hash (`27d5ce7f` / v5), while the corresponding `save` steps were bumped to v6.1.0. Although `restore` and `save` are independent actions and backward-compatible in practice, having them at different major versions is inconsistent and makes auditing the dependency harder. Consider bumping the restore steps to the same major version.

How can I resolve this? If you propose a fix, please make it concise.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
.github/workflows/soop-encode.yml:105-112
**Stale version comment after major-version bump**

Both updated `save` steps carry `# v5` comments, but `55cc834` corresponds to v6.1.0. A reader relying on the comment to audit the pinned version will see the wrong major version.

### Issue 2 of 2
.github/workflows/soop-encode.yml:59-73
**`restore` steps still pinned to v5 while `save` steps are now v6**

The two `actions/cache/restore` steps still use the old hash (`27d5ce7f` / v5), while the corresponding `save` steps were bumped to v6.1.0. Although `restore` and `save` are independent actions and backward-compatible in practice, having them at different major versions is inconsistent and makes auditing the dependency harder. Consider bumping the restore steps to the same major version.

_{Reviews (1): Last reviewed commit: "chore(deps): bump actions/cache/save fro..." | Re-trigger Greptile}

codacy-production · 2026-07-01T16:59:51Z

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer}
_{TIP This summary will be updated as you push new changes.}

greptile-apps · 2026-07-01T16:59:52Z

+        uses: actions/cache/save@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v5
        if: always()
        with:
          path: .soop/cache/semantic-cache.db*
          key: semantic-cache-${{ github.sha }}

      - name: Save tree-sitter parser cache
-        uses: actions/cache/save@27d5ce7f107fe9357f9df03efb73ab90386fccae # v5
+        uses: actions/cache/save@55cc8345863c7cc4c66a329aec7e433d2d1c52a9 # v5


Stale version comment after major-version bump

Both updated save steps carry # v5 comments, but 55cc834 corresponds to v6.1.0. A reader relying on the comment to audit the pinned version will see the wrong major version.

Prompt To Fix With AI

This is a comment left during a code review. Path: .github/workflows/soop-encode.yml Line: 105-112 Comment: **Stale version comment after major-version bump** Both updated `save` steps carry `# v5` comments, but `55cc834` corresponds to v6.1.0. A reader relying on the comment to audit the pinned version will see the wrong major version. How can I resolve this? If you propose a fix, please make it concise.

dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 1, 2026

greptile-apps Bot reviewed Jul 1, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(deps): bump actions/cache/save from 5.0.5 to 6.1.0#320

chore(deps): bump actions/cache/save from 5.0.5 to 6.1.0#320
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/cache/save-6.1.0

dependabot Bot commented on behalf of github Jul 1, 2026 •

edited by cubic-dev-ai Bot

Loading

Uh oh!

greptile-apps Bot commented Jul 1, 2026 •

edited

Loading

Comments Outside Diff (1)

Uh oh!

codacy-production Bot commented Jul 1, 2026

Uh oh!

greptile-apps Bot Jul 1, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

dependabot Bot commented on behalf of github Jul 1, 2026 • edited by cubic-dev-ai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v6.1.0

What's Changed

v6.0.0

What's Changed

v5.1.0

What's Changed

Releases

How to prepare a release

Changelog

6.1.0

6.0.0

5.0.4

5.0.3

5.0.2

Summary by cubic

Uh oh!

greptile-apps Bot commented Jul 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 4/5

Important Files Changed

Comments Outside Diff (1)

Uh oh!

codacy-production Bot commented Jul 1, 2026

Up to standards ✅

Uh oh!

greptile-apps Bot Jul 1, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

dependabot Bot commented on behalf of github Jul 1, 2026 •

edited by cubic-dev-ai Bot

Loading

greptile-apps Bot commented Jul 1, 2026 •

edited

Loading